Columbia Kermit/kermit.zip/newsgroups/misc.19960425-19960715/[e-mail] _Sat Jun 22 20:54:04 1996.msg

Internet Message Format | 2020-01-01 | 4KB

Return-Path: [e-mail]
Received: from apakabar.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30]) by watsun.cc.columbia.edu (8.7.5/8.7.3) with ESMTP id UAA21782 for <[e-mail]>; Sat, 22 Jun 1996 20:54:03 -0400 (EDT)
Received: (from news@localhost) by apakabar.cc.columbia.edu (8.7.5/8.7.3) id UAA25607 for kermit.misc@watsun; Sat, 22 Jun 1996 20:54:02 -0400 (EDT)
Path: news.columbia.edu!sol.ctr.columbia.edu!spool.mu.edu!howland.reston.ans.net!usc!chi-news.cic.net!news.compuserve.com!news.production.compuserve.com!news
From: Kelvin Smith <[e-mail]>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Greek in terminal emulation
Date: 23 Jun 1996 00:38:00 GMT
Organization: CompuServe, Inc. (1-800-689-0736)
Lines: 53
Message-ID: <4qi3l8$4ht$[e-mail]>
References: <4q916a$[e-mail]>

In message <4q916a$[e-mail]>,
  [e-mail] (Frank da Cruz) wrote:

> First, let's rule out the possibility that somehow a different code
> page is being loaded.  In a session in which you are seeing Greek,
> what happens if you type "run chcp" at the MS-Kermit> prompt?
> I expect it will say that your code page is 437, which does include
> some Greek characters.

Yes, I'm using code page 437.

> Second, what about your PARITY and TERMINAL BYTESIZE settings?  For
> using RSTS/E, I expect they should be NONE and 7, respectively (I don't
> remember RSTS that well -- maybe it needs EVEN parity).

Under SHOW TERM, parity is listed as "None (8-bit data)".

> So if your code page is 437 and your communications are 7-bit, you should
> not see any Greek.  If you are, my next guess would be that somebody is
> playing an elaborate trick on you.  Because if your TERMINAL CHARACTER-SET
> is LATIN1, there is no way you would ever see a Greek character on your
> screen, except lowercase mu, which is the only Greek character that is
> part of Latin Alphabet 1.  (But if your TERMINAL CHARACTER-SET is TRANSPARENT
> then you could see some Greek if your code page is 437.)

> Such a trick could be accomplished by loading a nonstandard font that
> had Greek characters in the ASCII positions, or by using SET TRANSLATE
> INPUT commands in some file that MS-DOS Kermit is executing.

The possibility of such a trick being played on me is extremely remote.
I ftp'ed Kermit directly from Columbia.  No one else in my office of
4 people has the technical skills to pull off a trick like this (I set
up all the programs for them, not the other way around), and the PC
is not physically accessible to anyone outside the office.

> So after SET PORT COM4 and seeing Greek, escape back to the MS-Kermit>
> prompt and look carefully at what is reported by SHOW TERMINAL and SHOW
> COMMUNICATIONS.

I can't reproduce this problem at will, but the last time it happened
I had the Greek version (running on COM4) and a properly displaying
version (running on COM2) running in separate sessions under Windows.
I task-switched back and forth between the two looking at every item
in SHOW COMM and SHOW TERM.  The only things that varied were the
port-specific settings (COM number, port address, speed).  Twice I've
changed the terminal character-set when I was seeing Greek, even
though SHOW TERM showed the active character-set as Latin1.  Setting
it to either ASCII or Latin1 cleared the condition (previous characters
were unchanged, but anything displayed following was in normal form).
IOW, resetting it to Latin1, even when Kermit claimed it was already
using Latin1, cleared the condition.

Kelvin Smith